Create sentry_project_membership Resource Type
#652
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a use-case where I would like to attach teams to a pre-existing project, without having to manage the entire project via Terraform. This PR implements the beginnings of a
sentry_project_membershipresource, which one could use to:data "sentry_project" ...The idea here is very similar to AWS's use of
ingress/egresson aws_security_group vs. declaring separate aws_vpc_security_group_ingress_rules. With the former you have to manage the entire security group in one place, and with the latter you can distribute management throughout your TF workspace.This approach has some really sharp edges sitting alongside the
teamsfield onsentry_project, so I understand if you aren't interested in accepting a contribution like this, but I would be interested to chat it through with you!